Skip to content

Conversation

@mosabua
Copy link
Member

@mosabua mosabua commented Nov 7, 2025

Description

Assemble the release notes for Trino Gateway 17 release and adjust rest of docs to version 17.

Release date is set to the planned date following our monthly release cadence.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

Verification for each pull request

Format: PR/issue number, ✅ / ❌ rn ✅ / ❌ docs
✅ rn - release note added and verified, or assessed to be not necessary, set to ❌ rn before completion
✅ docs - need for docs assessed and merged, or assessed to be not necessary, set to ❌ docs before completion

Any dates missing in the list just had no merged PRs.

19 Sep 2025

30 Sep 2025

1 Oct 2025

9 Oct 2025

24 Oct 2025

29 Oct 2025

30 Oct 2025

3 Nov 2025

28 Nov 2025

29 Nov 2025

10 Dec 2025

11 Dec 2025

14 Dec 2025

18 Dec 2025

30 Dec 2025

31 Dec 2025

2 Jan 2026

3 Jan 2026

4 Jan 2026

5 Jan 2026

6 Jan 2026

7 Jan 2026

8 Jan 2026

10 Jan 2026

11 Jan 2026

14 Jan 2026

15 Jan 2026

18 Jan 2026

19 Jan 2026

@mosabua mosabua changed the title [WIP] Add Trino Gateway 17 release notes Add Trino Gateway 17 release notes Jan 10, 2026
@mosabua
Copy link
Member Author

mosabua commented Jan 15, 2026

Really need some review here @trinodb/maintainers-gateway so we can move to a release soon

Comment on lines 29 to 30
* [:warning: Breaking change:](#breaking) Remove defunct email notifier.
([#843](https://github.com/trinodb/trino-gateway/pull/843))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is a breaking change. The PR removed unused code.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know for sure it was unused? I am not sure .. there might have been private extensions .. but maybe we don't consider that as breaking

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need to write release notes for "private extensions". This project isn't a library.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Private extensions are not officially supported, so I don’t think a release note is needed. Anyone who can implement private extensions and patch the source code should be able to figure it out themselves.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay. I removed the breaking label but left the entry there. Okay?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no need to add this entry, since the feature didn't exist from a user perspective.

Copy link
Member

@Chaho12 Chaho12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Member

@vishalya vishalya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for including the links to the merged PR list for the older versions as well.
LGTM!

Also backfill links to milestones for older releases.
@mosabua
Copy link
Member Author

mosabua commented Jan 21, 2026

All comments addressed. Set date to tomorrow for now. Hopefully @martint can cut a release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

5 participants